CI Commands

The following CI workflows run automatically on every push and pull request:

The following commands can be used by maintainers to trigger additional tests that require access to secrets:

Note: Only repository maintainers (OWNER association) can trigger /metaci commands. After commenting the command, a maintainer must also navigate to the Actions tab and approve the deployment to the graph-api-access environment before the jobs will run. See the approval guidelines for what to approve or reject.

@claude can you fix the ci issues?

Claude finished @luccabb's task in 1m 44s —— View job

Fixing CI Issues

• Gather context: check CI status
• Identify failing tests/checks
• Determine the fix
• Attempt commit and push — blocked by branch protection ("Meta CLA Check")

Root Cause

Both shelper-tests and shelper-lint are failing because shelper/go.mod is missing the indirect dependencies that testify requires. The CI error is:

go: updates to go.mod needed; to update it:
    go mod tidy

Fix

Apply this change to shelper/go.mod — add the indirect dependencies:

 require github.com/stretchr/testify v1.10.0
+
+require (
+	github.com/davecgh/go-spew v1.1.1 // indirect
+	github.com/pmezard/go-difflib v1.0.0 // indirect
+	gopkg.in/yaml.v3 v3.0.1 // indirect
+)

Or simply run from the repo root:

cd shelper && go mod tidy

Then commit and push the updated shelper/go.mod (and shelper/go.sum if it changes).

Note: I couldn't push this fix directly because pushes to your branch are blocked by the "Meta CLA Check" repository rule. You'll need to apply this change yourself.

View failing CI run | Branch

@luccabb has imported this pull request. If you are a Meta employee, you can view this in D96259734.

@luccabb has exported this pull request. If you are a Meta employee, you can view the originating Diff in D96259734.